Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add test for error propagation. #120

Merged
merged 1 commit into from
Oct 11, 2024
Merged

Conversation

aljones15
Copy link
Contributor

Adds a new statement about error propagation in the create step:

If the algorithm produces an error, the error MUST be propagated and SHOULD convey the error type.

Comment on lines +253 to +254
// FIXME this test should look for a propagated error such as
// PROOF_GENERATION_ERROR
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this fixable before we merge this one?

Copy link
Contributor Author

@aljones15 aljones15 Oct 2, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we need to inform the implementers that they need to start returning error objects when issuance fails and verification fails. Currently most implementers do return verification results. Basically we need to make implementers aware that https://w3c-ccg.github.io/vc-api/#error-handling VC-API Error Handling is a thing. I also thought the VC-API group came to consensus at some point about standardized error handling, but it looks like they have not although error codes in the specs do suggest there is a common error object for data integrity at least. So perhaps we should ask implementers for the test suite to return https://w3c.github.io/vc-data-integrity/#processing-errors Problem Details in the future. Basically right now we not have informed implementers to return problem details so asserting on those error codes in data returned on fail seems unfair. I can add a section to the README about this as we really need those problem details for the suite.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BigBlueHat revised README is here: #122

Those details should probably be in the implementations README to.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

w3c-ccg/vc-api#418

this is the PR that defines it, ideally there would be a problemDetails property in the response and we just need to ensure there's at least 1 item in that array, since there's no instruction on what to look for in that statement.

@aljones15 aljones15 merged commit 1f5c835 into main Oct 11, 2024
1 of 2 checks passed
@aljones15 aljones15 deleted the new-create-proof-algorithm branch October 11, 2024 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants